JBoss.orgCommunity Documentation

Chapter 4. Shell Command Line

4.1. Introduction
4.2. Starting
4.3. SCCP Management
4.3.1. Rule Management
4.3.2. Address Management
4.3.3. Remote Signaling Point Management
4.3.4. Remote Sub-System Management
4.4. M3UA Management
4.4.1. M3UA Management - SCTP
4.4.2. M3UA Management

Mobicents SS7 Stack provides Shell client to manage configuration of SS7 Stack Services. This chapter describes how to install and start client. Also it describes available commands and provides examples. To see examples of specific flow, to perform certain tasks, please refer to sections in chapter devoted to SCCP or M3UA .

Shell client can be started with following command from $JBOSS_HOME/bin :

[$] ./ss7-run.sh

Once console starts, it will print following information:

=========================================================================

Mobicents SS7: release.version=1.0.0-SNAPSHOT
This is free software, with components licensed under the GNU General Public License
version 2 and other licenses. For further details visit http://mobicents.org
=========================================================================

mobicents>
		

The ss7-run script supports following options

Usage: SS7 [OPTIONS]
Valid Options
-v           Display version number and exit
-h           This help screen

		

Shell needs to connect to managed instance. Command to connect has following structure:

ss7 connect <IP> <PORT> 

Note

Host IP and port are optional, if not specified, shell will try to connect to 127.0.0.1:3435

Command to disconnect has following structure:

ss7 discconnect 

SCCP provides connectionless and connection-oriented network services. This includes address(GTT) translation and routing, flow control segmentation and reassembly.

A global title is an address (e.g., a dialed 800 number, calling card number, or mobile subscriber identification number) which is translated by SCCP into a destination point code and subsystem number. A subsystem number uniquely identifies an application at the destination signaling point. SCCP is used as the transport layer for TCAP -based services

As SCCP acts as message router, it requires means to configure routing information. CLI provides way to easily manage routing rules information in Mobicents SCCP implementation.

User should also configure the remote subsystem number and remote signaling pointcode. In some cases where global title is used, SCCP will only require configuring of remote signaling pointcode and configuring of remote subsystem is not required.

SCCP routing rules are managed by sccp rule command. It allows to perform following:

Rule can be create by issuing command with following structure:

sccp rule create <id> <mask> <address-indicator> <point-code> <subsystem-number> <translation-type> <numbering-plan>  
<nature-of-address-indicator> <digits> <primary-address-id> <backup-address-id>

This command should be specified after primary_add and backup_add are configured. Please refer Section 4.3.2, “Address Management” on how to configure primary_add and backup_add

<id>

A unique number to identify this rule

<mask>

mask defines which part of the originally dialed digits remains in the translated digits and which part is replaced by the digits from primary or backup address. mask is divided into sections by separator /. The number of sections in mask should be equal to sections in digits passed in this command and sections in primary or backup address


<address-indicator>

The address indicator is the first field in SCCP Party Address(called/calling) and is one octet in length. Its function is to indicate which information elements are present so that the address can be interpreted, in other words, it indicates the type of addressing information that is to be found in the address field. The addressing information from original global title is then compared with passed address information to match the rule.

<point-code>

Point code. This is ignored if bit 0 of address-indicator is not set.

<subsystem-number>

Subsystem Number. This is ignored if bit 1 of address-indicator is not set.

<translation-type>

Translation type. This is ignored if GT Indicator is 0000 or 0001


<numbering-plan>

The Number Plan (NP) field specifies the numbering plan that the address information follows. This is ignored if GT Indicator is 0000, 0001 or 0010

<nature-of-address-indicator>

The Nature of Address Indicator (NAI) field defines the address range for a specific numbering plan. This is only used if GT Indicator is 0100

<digits>

Specifies the string of digits divided into subsections using separator '/' depending on if mask contains separator. The dialed digits should match with theses digits as per rule specified bellow


<primary-address-id>

Identifies the SCCP Address used as the primary translation

<backup-address-id>

Identifies the SCCP Address used as the backup translation incase if pointcode specified by primary address is not available


The command is used to define primary or backup address of translation. The global title address information of this command is combined with the global title being translated by examining the mask provided in the sccp rule create command.The syntanx remains same except for primary address sccp primary_add is used and for backup address sccp backup_add is used

Address can be create by issuing command with following structure:

<id>

A unique number to identify this address

<address-indicator>

The address indicator is the first field in SCCP Party Address(called/calling) and is one octet in length. Its function is to indicate which information elements are present so that the address can be interpreted, in other words, it indicates the type of addressing information that is to be found in the address field. The addressing information from original global title is then compared with passed address information to match the rule.

<point-code>

Point code. This is ignored if bit 0 of address-indicator is not set.

<subsystem-number>

Subsystem Number. This is ignored if bit 1 of address-indicator is not set.

<translation-type>

Translation type. This is ignored if GT Indicator is 0000 or 0001


<numbering-plan>

The Number Plan (NP) field specifies the numbering plan that the address information follows. This is ignored if GT Indicator is 0000, 0001 or 0010

<nature-of-address-indicator>

The Nature of Address Indicator (NAI) field defines the address range for a specific numbering plan. This is only used if GT Indicator is 0100

<digits>

The global title address information to translate to, specified as string of digits divided into subsections using separator '/' depending on if mask contains separator.

In addition the digits string can contain




SCCP resources includes remote signaling point and remote subsytem. Each remote subsystem that SCCP can communicate with must be configured using sccp rss command

This command should be specified after remote signaling point is configured. Please refer Section 4.3.3, “Remote Signaling Point Management” on how to configure remote signaling point

M3UA stack is also responsible to manage the SCTP Associations.

M3UA - SCTP is managed by sctp command. It allows to perform following:

Association can be created by issuing command with following structure:

sctp association create <assoc-name> <CLIENT | SERVER> <server-name> <peer-ip> <peer-port> <host-ip> <host-port> <socket-type>

Where:



M3UA is managed by m3ua command. It allows to perform following:

Application Server (AS) can be created by issuing command with following structure:

m3ua as create <as-name> <AS | SGW | IPSP> mode <SE | DE> ipspType <client | server> rc <routing-context> traffic-mode <traffic mode> <network-appearance>

Where:

as-name

simple string name, which identifies AS. Make sure this is unique. This is mandatory parameter

AS | SGW | IPSP

Specify if this is of type AS or SGW or IPSP. This is mandatory parameter

SE | DE

Specify if the single or double exchange of ASP State Maintenance (ASPSM) and ASP Traffic Maintenance (ASPTM) messages should be performed. This is mandatory parameter.

client | server

If As if of type IPSP, speicfy here if its client or server type.

routing-context

refers to Routing Context already configured on M3UA stack on SGW side. This is optional parameter. If no Routing Context is passed, Application Server Process (assigned to this AS) may not be configured to process signalling traffic related to more than one Application Server, over a single SCTP Association

Also if ASP is configured to process siganlling traffic from always one AS, irrespective of received messages have routing context set or not, it will always be delieverd to AS for further processing. However if ASP is configured to process siganlling traffic related to more than one AS over a single SCTP Association and signalling message is received without RC, it drops the message and sends back Error message. Respective log4j error is also logged.

traffic-mode

Traffic mode for ASP's. By default its loadshare. Mobicents M3UA only supports loadshare and override, broadcast is not supported.

network-appearance

The Network Appearance is a M3UA local reference shared by SG and AS (typically an integer) that, together with an Signaling Point Code, uniquely identifies an SS7 node by indicating the specific SS7 network to which it belongs. It can be used to distinguish between signalling traffic associated with different networks being sent between the SG and the ASP over a common SCTP association. This is optional.